Outdated Terraform Dependency and Potential Transition to OpenTofu

[Shion1305]

Note

This issue was originally created on #1931 but closed due to no activity. I reraised the issue here.

Hi,

While debugging Terraformer for #1932, I noticed that it uses an outdated version of hashicorp/terraform. The current version in use, hashicorp/terraform@v0.12.31, includes explicit references to version 0.12.31 in its gRPC communications:

• https://github.com/hashicorp/terraform/blob/ff2f9bef36189b28f5e3a91dd6cdb39c2ffdcbe0/plugin/grpc_provider.go#L288-L295
• https://github.com/hashicorp/terraform/blob/ff2f9bef36189b28f5e3a91dd6cdb39c2ffdcbe0/version/version.go#L14

I attempted to upgrade the hashicorp/terraform dependency, but it seems that hashicorp/terraform no longer supports imports from other modules, as discussed here:

• get error when using go get command hashicorp/terraform#35695 (comment)

Although I am not deeply familiar with the internal workings of Terraform, it seems that Terraformer may need to transition to OpenTofu in order to maintain its functionality going forward.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[Shion1305]

Looking forward for any comments

[MridulTi]

I think terraformer code needs to be updated for terraform languange as its quite outdated especially for AWS provider, part from that @Shion1305 , why do you feel transitioning to OpenTofu would be better?

[Shion1305]

@MridulTi Thanks for your input. I haven't worked with the terraformer codebase recently, but when I last attempted to modify it, I encountered difficulty resolving dependencies for hashicorp/terraform. This issue might be related to Terraform's transition away from being fully open source. That's partly why I was curious about the potential benefits of transitioning to OpenTofu.